Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af75ef70d3bded131db54abd4511e71fc63156550f6e0ac6dc79b61780d879ec

Tx prefix hash: 5e74f0771e68ed4775e494ddbe432264334b66d9023ad44851f784122574af78
Tx public key: 591e5238bc8c01e1a02928b43aa63e6405d8c958e1df3a044d846d712f3dd95b
Timestamp: 1702681613 Timestamp [UCT]: 2023-12-15 23:06:53 Age [y:d:h:m:s]: 01:335:01:25:58
Block: 913972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498333 RingCT/type: yes/0
Extra: 01591e5238bc8c01e1a02928b43aa63e6405d8c958e1df3a044d846d712f3dd95b02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04cc80968928e247a3d1c4e7b487eb8c540529ebd79a77fe8f67d8ae0895369c 0.600000000000 1371252 of 15

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": 913982, "vin": [ { "gen": { "height": 913972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04cc80968928e247a3d1c4e7b487eb8c540529ebd79a77fe8f67d8ae0895369c" } } ], "extra": [ 1, 89, 30, 82, 56, 188, 140, 1, 225, 160, 41, 40, 180, 58, 166, 62, 100, 5, 216, 201, 88, 225, 223, 58, 4, 77, 132, 109, 113, 47, 61, 217, 91, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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