Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d8ec60e8c8fe4f0dec6f744434d63580427ce2f53f6b38d1622d4c11106fed0

Tx prefix hash: d3bd7e4ca3a23fb44b3d614a634e52471d775486da8ff3be63c2223e88704349
Tx public key: 6e30ad090a2cf8d65a535e3d770641fcb8d785403d46f9eae20afa5664cb278a
Timestamp: 1718178046 Timestamp [UCT]: 2024-06-12 07:40:46 Age [y:d:h:m:s]: 01:150:02:30:42
Block: 1042457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365840 RingCT/type: yes/0
Extra: 016e30ad090a2cf8d65a535e3d770641fcb8d785403d46f9eae20afa5664cb278a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 652d8a6d75c93293a649e39e42021188e012e4d63f28350dd431fa38b0a2d7fd 0.600000000000 1511382 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": 1042467, "vin": [ { "gen": { "height": 1042457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "652d8a6d75c93293a649e39e42021188e012e4d63f28350dd431fa38b0a2d7fd" } } ], "extra": [ 1, 110, 48, 173, 9, 10, 44, 248, 214, 90, 83, 94, 61, 119, 6, 65, 252, 184, 215, 133, 64, 61, 70, 249, 234, 226, 10, 250, 86, 100, 203, 39, 138, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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