Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b3fdd9171ba221ac283d897e1a7f31bf39ea6af87e8089d436271963f1f326a9

Tx prefix hash: 0ae9ff7761245b04b33abc5f3e68211ad5e7b8e83397630c08570f192b8c65db
Tx public key: f5e931f70c1ce48f2aff93849daa45eb77b347d2e962837a2ff7ab49ae032083
Timestamp: 1730948340 Timestamp [UCT]: 2024-11-07 02:59:00 Age [y:d:h:m:s]: 00:017:03:34:07
Block: 1148236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12267 RingCT/type: yes/0
Extra: 01f5e931f70c1ce48f2aff93849daa45eb77b347d2e962837a2ff7ab49ae0320830211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b64374ce7492007d1af221cbef88f1a163c36ef2a77e7695c35e6b3998dce84 0.600000000000 1633035 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1148246, "vin": [ { "gen": { "height": 1148236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b64374ce7492007d1af221cbef88f1a163c36ef2a77e7695c35e6b3998dce84" } } ], "extra": [ 1, 245, 233, 49, 247, 12, 28, 228, 143, 42, 255, 147, 132, 157, 170, 69, 235, 119, 179, 71, 210, 233, 98, 131, 122, 47, 247, 171, 73, 174, 3, 32, 131, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8