Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848affd02316566a9e2cbbaf20fe98217c990ada3c595868e51948a114d2d84b

Tx prefix hash: 31afc84e1bfc65984c59a06215aeec7455567ae7db860a04842b995bd55a5881
Tx public key: ecf21f8a27049a0e1bca8d1fe876a413c3a1419e516c8abf3271db82296fe210
Timestamp: 1681394051 Timestamp [UCT]: 2023-04-13 13:54:11 Age [y:d:h:m:s]: 01:363:07:08:18
Block: 737728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520936 RingCT/type: yes/0
Extra: 01ecf21f8a27049a0e1bca8d1fe876a413c3a1419e516c8abf3271db82296fe2100211000000015029cbac000000000000000000

1 output(s) for total of 2.205977668000 dcy

stealth address amount amount idx
00: 65f87cbcf6563a9f662a57c5eadc50dca2b1fab8e2993972a321a9fc225cb2e8 2.205977668000 1184321 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": 737738, "vin": [ { "gen": { "height": 737728 } } ], "vout": [ { "amount": 2205977668, "target": { "key": "65f87cbcf6563a9f662a57c5eadc50dca2b1fab8e2993972a321a9fc225cb2e8" } } ], "extra": [ 1, 236, 242, 31, 138, 39, 4, 154, 14, 27, 202, 141, 31, 232, 118, 164, 19, 195, 161, 65, 158, 81, 108, 138, 191, 50, 113, 219, 130, 41, 111, 226, 16, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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