Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 503f8049c5997e70b21470e3e017f85c2c6fd50cdb82b4d1a73ec039af1bb9af

Tx prefix hash: 34f121284857fe005c3679ddc1c4ef27099a754677a969582e9e2c2fcceb5360
Tx public key: d6f9abe9c4a4a4a3a30a6f67aaf92ec64dd057869ec568c550f6f510723f4410
Timestamp: 1727487471 Timestamp [UCT]: 2024-09-28 01:37:51 Age [y:d:h:m:s]: 00:189:07:40:11
Block: 1119631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135115 RingCT/type: yes/0
Extra: 01d6f9abe9c4a4a4a3a30a6f67aaf92ec64dd057869ec568c550f6f510723f441002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6ae392fe30dd8589b7745a7c013876fb59b798474b80f32ddb1352b9d6626b9 0.600000000000 1601258 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": 1119641, "vin": [ { "gen": { "height": 1119631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6ae392fe30dd8589b7745a7c013876fb59b798474b80f32ddb1352b9d6626b9" } } ], "extra": [ 1, 214, 249, 171, 233, 196, 164, 164, 163, 163, 10, 111, 103, 170, 249, 46, 198, 77, 208, 87, 134, 158, 197, 104, 197, 80, 246, 245, 16, 114, 63, 68, 16, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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