Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3cb06fea29ef679bd39b854e42c5b5c4dfba570176c9a1710c6926d9b1f7040

Tx prefix hash: c168299f18d859982322e46ec38469cca563157b954d7101aa5ac89a04ddcb5b
Tx public key: e71166506aecf1fdf9ae1694d04f52c163d8172aaa039030225d3c267714bfe9
Timestamp: 1725630364 Timestamp [UCT]: 2024-09-06 13:46:04 Age [y:d:h:m:s]: 01:064:17:51:35
Block: 1104236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304701 RingCT/type: yes/0
Extra: 01e71166506aecf1fdf9ae1694d04f52c163d8172aaa039030225d3c267714bfe9021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26c3732efb70d2cd29fc62f9ae565564eaef22d2a07d1149b045c8c307ad224d 0.600000000000 1581315 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": 1104246, "vin": [ { "gen": { "height": 1104236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26c3732efb70d2cd29fc62f9ae565564eaef22d2a07d1149b045c8c307ad224d" } } ], "extra": [ 1, 231, 17, 102, 80, 106, 236, 241, 253, 249, 174, 22, 148, 208, 79, 82, 193, 99, 216, 23, 42, 170, 3, 144, 48, 34, 93, 60, 38, 119, 20, 191, 233, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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