Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad056f8a7927aabf6c1129e6245507d50c067ce87254a5352cd5a3881ef9a825

Tx prefix hash: 84cd4cba2a0164aa41af3ae3701469f4d176644f56f733d1e2b57535fc58ee30
Tx public key: e44555b151f0fa374424af2af65ba41466327d9322b1a8ef57b53b459ac2fed3
Timestamp: 1647758403 Timestamp [UCT]: 2022-03-20 06:40:03 Age [y:d:h:m:s]: 02:278:23:32:50
Block: 462351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 718929 RingCT/type: yes/0
Extra: 01e44555b151f0fa374424af2af65ba41466327d9322b1a8ef57b53b459ac2fed3021100000002bf7ee4e7000000000000000000

1 output(s) for total of 18.031815981000 dcy

stealth address amount amount idx
00: 0c85de687b66a09dacbb03cf5d2e3d359f32e7a30cbb747259f1de5d3b512d4b 18.031815981000 879788 of 0

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": 462361, "vin": [ { "gen": { "height": 462351 } } ], "vout": [ { "amount": 18031815981, "target": { "key": "0c85de687b66a09dacbb03cf5d2e3d359f32e7a30cbb747259f1de5d3b512d4b" } } ], "extra": [ 1, 228, 69, 85, 177, 81, 240, 250, 55, 68, 36, 175, 42, 246, 91, 164, 20, 102, 50, 125, 147, 34, 177, 168, 239, 87, 181, 59, 69, 154, 194, 254, 211, 2, 17, 0, 0, 0, 2, 191, 126, 228, 231, 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