Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1e77c3f666f4fae1e34ddabaa634703be0181b2c3230626e59f13e732300db7

Tx prefix hash: ed4e3029f121c553f0d3ccc5f64d17264dac2785ec54026c4f12f8a1605cf03d
Tx public key: cf0b0c71c4d915ee08e7c05a6a99bc48a6eb439991434c946e011f76ba8b1cf2
Timestamp: 1743473052 Timestamp [UCT]: 2025-04-01 02:04:12 Age [y:d:h:m:s]: 00:230:11:11:27
Block: 1251658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162456 RingCT/type: yes/0
Extra: 01cf0b0c71c4d915ee08e7c05a6a99bc48a6eb439991434c946e011f76ba8b1cf2021100000005a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62cd634a669f1eef734bb176700536243399546d5bcff59c64c092aa7a04f5d3 0.600000000000 1738727 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": 1251668, "vin": [ { "gen": { "height": 1251658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62cd634a669f1eef734bb176700536243399546d5bcff59c64c092aa7a04f5d3" } } ], "extra": [ 1, 207, 11, 12, 113, 196, 217, 21, 238, 8, 231, 192, 90, 106, 153, 188, 72, 166, 235, 67, 153, 145, 67, 76, 148, 110, 1, 31, 118, 186, 139, 28, 242, 2, 17, 0, 0, 0, 5, 162, 237, 1, 107, 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