Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de3f75ab9d25c741146d645047610e7baabd17acd95212e5b903ddcdaa44b8b3

Tx prefix hash: cedb4d106e02b9c60adf2f9412c673a20de31d92ada429234aab6774564c4b91
Tx public key: 3c57ec64a4a90afa99e88a58181e65dc56612aa1ab98fd18a6d22acbeb45133a
Timestamp: 1727134384 Timestamp [UCT]: 2024-09-23 23:33:04 Age [y:d:h:m:s]: 00:214:16:37:32
Block: 1116700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153275 RingCT/type: yes/0
Extra: 013c57ec64a4a90afa99e88a58181e65dc56612aa1ab98fd18a6d22acbeb45133a02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d8c6494483e126b276555a9cd53999d73c8b0ababc874ef3e9e7a2a093f2c0a 0.600000000000 1597277 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": 1116710, "vin": [ { "gen": { "height": 1116700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d8c6494483e126b276555a9cd53999d73c8b0ababc874ef3e9e7a2a093f2c0a" } } ], "extra": [ 1, 60, 87, 236, 100, 164, 169, 10, 250, 153, 232, 138, 88, 24, 30, 101, 220, 86, 97, 42, 161, 171, 152, 253, 24, 166, 210, 42, 203, 235, 69, 19, 58, 2, 17, 0, 0, 0, 7, 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