Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e155c3e7d6287902cb7a6ad8d197af9c40a8a3d2b74562f9267f19a3342deb8b

Tx prefix hash: bf2b707437ea04d46798736635b76c00284579f941f6cc36aa619c3c8666c9e2
Tx public key: bfe244e944d5e900527b29d427e3ffecf1599935f894b08d8d980ed125bf0f95
Timestamp: 1639396693 Timestamp [UCT]: 2021-12-13 11:58:13 Age [y:d:h:m:s]: 03:066:01:57:40
Block: 394600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 825922 RingCT/type: yes/0
Extra: 01bfe244e944d5e900527b29d427e3ffecf1599935f894b08d8d980ed125bf0f9502110000001beaa12622000000000000000000

1 output(s) for total of 30.236168234000 dcy

stealth address amount amount idx
00: 04386ab92398170dd75393af75ec6807dfdc2dd5ca0ac9634d0ecf85da1667ab 30.236168234000 792245 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": 394610, "vin": [ { "gen": { "height": 394600 } } ], "vout": [ { "amount": 30236168234, "target": { "key": "04386ab92398170dd75393af75ec6807dfdc2dd5ca0ac9634d0ecf85da1667ab" } } ], "extra": [ 1, 191, 226, 68, 233, 68, 213, 233, 0, 82, 123, 41, 212, 39, 227, 255, 236, 241, 89, 153, 53, 248, 148, 176, 141, 141, 152, 14, 209, 37, 191, 15, 149, 2, 17, 0, 0, 0, 27, 234, 161, 38, 34, 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