Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49c54aef245a3422512b1213ff327cbec5d77a12992c15991bafe35d3b1498bb

Tx prefix hash: e0a077a33ef055d58861117173a120c0394ec7d9a04fa2502254848e583c5f62
Tx public key: bb78a9045552f722c9fb5ff068cf853268cf74e22f997fe9c33a6625ab1f3d8e
Timestamp: 1577722637 Timestamp [UCT]: 2019-12-30 16:17:17 Age [y:d:h:m:s]: 05:017:14:34:54
Block: 35154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1162561 RingCT/type: yes/0
Extra: 01bb78a9045552f722c9fb5ff068cf853268cf74e22f997fe9c33a6625ab1f3d8e0211000000084ac5aa02000000000000000000

1 output(s) for total of 469.376194546000 dcy

stealth address amount amount idx
00: 11c52418bc9d0abda856e26eff9ce0e97003fc527c796ba7d137c3d1559c5794 469.376194546000 59218 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": 35164, "vin": [ { "gen": { "height": 35154 } } ], "vout": [ { "amount": 469376194546, "target": { "key": "11c52418bc9d0abda856e26eff9ce0e97003fc527c796ba7d137c3d1559c5794" } } ], "extra": [ 1, 187, 120, 169, 4, 85, 82, 247, 34, 201, 251, 95, 240, 104, 207, 133, 50, 104, 207, 116, 226, 47, 153, 127, 233, 195, 58, 102, 37, 171, 31, 61, 142, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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