Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddd50440e4d79db8167b38fee1149416d1a628b3662a7717fad717f8bd9f7c32

Tx prefix hash: e9958b29c65b8178c8424b4839ccc8abb0aaefed9f7c2a955a454d2ce4371cac
Tx public key: 61dedc1a1e50b73191dec46d22761a942e4277649033902f985c3de3d0534318
Timestamp: 1580570032 Timestamp [UCT]: 2020-02-01 15:13:52 Age [y:d:h:m:s]: 05:122:05:46:55
Block: 56630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1239240 RingCT/type: yes/0
Extra: 0161dedc1a1e50b73191dec46d22761a942e4277649033902f985c3de3d053431802110000000617786bcf000000000000000000

1 output(s) for total of 398.439260185000 dcy

stealth address amount amount idx
00: b2aa93ee55d36003fea07b4940867a1559eab7ad988bde1e1ab8b282d5a19377 398.439260185000 104403 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": 56640, "vin": [ { "gen": { "height": 56630 } } ], "vout": [ { "amount": 398439260185, "target": { "key": "b2aa93ee55d36003fea07b4940867a1559eab7ad988bde1e1ab8b282d5a19377" } } ], "extra": [ 1, 97, 222, 220, 26, 30, 80, 183, 49, 145, 222, 196, 109, 34, 118, 26, 148, 46, 66, 119, 100, 144, 51, 144, 47, 152, 92, 61, 227, 208, 83, 67, 24, 2, 17, 0, 0, 0, 6, 23, 120, 107, 207, 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