Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f322b35291dd2958d7db43aa71f5dda54958a67cfab8d660e87406f08069f799

Tx prefix hash: 2632cac3c1d8d4e5d0d45a4af6f3c2ccf10926187de8649a54abac5015dfa6a4
Tx public key: a710ec68e06ff7d4a7243df33db63c3ed9d3353394078e9e5073f95d7de822c0
Timestamp: 1577611728 Timestamp [UCT]: 2019-12-29 09:28:48 Age [y:d:h:m:s]: 04:333:20:58:32
Block: 34243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127692 RingCT/type: yes/0
Extra: 01a710ec68e06ff7d4a7243df33db63c3ed9d3353394078e9e5073f95d7de822c00211000000138a2ee0d9000000000000000000

1 output(s) for total of 472.649912818000 dcy

stealth address amount amount idx
00: 234d4637c3d235ff0305f1e1e55d0ee67541d7d64c0bf249f65a58ce00c3440a 472.649912818000 57616 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": 34253, "vin": [ { "gen": { "height": 34243 } } ], "vout": [ { "amount": 472649912818, "target": { "key": "234d4637c3d235ff0305f1e1e55d0ee67541d7d64c0bf249f65a58ce00c3440a" } } ], "extra": [ 1, 167, 16, 236, 104, 224, 111, 247, 212, 167, 36, 61, 243, 61, 182, 60, 62, 217, 211, 53, 51, 148, 7, 142, 158, 80, 115, 249, 93, 125, 232, 34, 192, 2, 17, 0, 0, 0, 19, 138, 46, 224, 217, 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