Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdd9d92d81eb1b147518f82b12117653b16e61e5c074a3c2df9fc16d820917e2

Tx prefix hash: 733be67f7a9fddf04ceb0eb4334782915d09f382d9064ccecee2b03e94f2e5d1
Tx public key: e89ad1aa65c40f2af45c30fc34b6a930f491f2f09b95ec01bacfcc22022e88a1
Timestamp: 1710785886 Timestamp [UCT]: 2024-03-18 18:18:06 Age [y:d:h:m:s]: 01:090:08:03:02
Block: 981189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325458 RingCT/type: yes/0
Extra: 01e89ad1aa65c40f2af45c30fc34b6a930f491f2f09b95ec01bacfcc22022e88a102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a07978918aae8c65f83cdeac28b52ea52460b57d229adc921f79f275faf6a6e7 0.600000000000 1441282 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": 981199, "vin": [ { "gen": { "height": 981189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a07978918aae8c65f83cdeac28b52ea52460b57d229adc921f79f275faf6a6e7" } } ], "extra": [ 1, 232, 154, 209, 170, 101, 196, 15, 42, 244, 92, 48, 252, 52, 182, 169, 48, 244, 145, 242, 240, 155, 149, 236, 1, 186, 207, 204, 34, 2, 46, 136, 161, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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