Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e59ffa9931ce553a06cf6789ddbdd0658650c5a1a6ce9f7f33bfd4e6c9e0a06

Tx prefix hash: 8a751d95bd6a89516f7cac6700aafaef177e98696c247b30794f1172182a41d5
Tx public key: e69c3386380fd134bca8e83a033448248ab54a101b9ae032a2d27e92fee892ff
Timestamp: 1722705094 Timestamp [UCT]: 2024-08-03 17:11:34 Age [y:d:h:m:s]: 00:081:18:13:24
Block: 1079979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58533 RingCT/type: yes/0
Extra: 01e69c3386380fd134bca8e83a033448248ab54a101b9ae032a2d27e92fee892ff021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d4a26e3ee3d0b7fb753d4a7338764fa4c6817a7bacafa7faa699cfc98c2240e 0.600000000000 1553160 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": 1079989, "vin": [ { "gen": { "height": 1079979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d4a26e3ee3d0b7fb753d4a7338764fa4c6817a7bacafa7faa699cfc98c2240e" } } ], "extra": [ 1, 230, 156, 51, 134, 56, 15, 209, 52, 188, 168, 232, 58, 3, 52, 72, 36, 138, 181, 74, 16, 27, 154, 224, 50, 162, 210, 126, 146, 254, 232, 146, 255, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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