Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a296c65e1ecae51066683ae352a9b31655acda9029c80fe9d62be61af44ff8e4

Tx prefix hash: 28fe44f7800f261e3580fff2d85d2fabd266da98f216246864040ad3c39331d3
Tx public key: bf4cb55ce71080c9c324cdb1247e6fdc087d2d0c04305a24a3ac6d67d3727708
Timestamp: 1577531558 Timestamp [UCT]: 2019-12-28 11:12:38 Age [y:d:h:m:s]: 05:067:20:41:58
Block: 33429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198386 RingCT/type: yes/0
Extra: 01bf4cb55ce71080c9c324cdb1247e6fdc087d2d0c04305a24a3ac6d67d37277080211000000034ac5aa02000000000000000000

1 output(s) for total of 475.594368188000 dcy

stealth address amount amount idx
00: 94620354982147195b48ac540f2197c85e0e563acc8269e946a1be53beb04685 475.594368188000 55970 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": 33439, "vin": [ { "gen": { "height": 33429 } } ], "vout": [ { "amount": 475594368188, "target": { "key": "94620354982147195b48ac540f2197c85e0e563acc8269e946a1be53beb04685" } } ], "extra": [ 1, 191, 76, 181, 92, 231, 16, 128, 201, 195, 36, 205, 177, 36, 126, 111, 220, 8, 125, 45, 12, 4, 48, 90, 36, 163, 172, 109, 103, 211, 114, 119, 8, 2, 17, 0, 0, 0, 3, 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