Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cb8c0aed3b764034524e01d47be8f5e11626c0b3d0036f47a68368d78c70634

Tx prefix hash: bc774bdeac95dd8e5c98fe6eb7bc26c0ea5d8fbce827c53a105e1ab63a27b2d4
Tx public key: 8613290735414a390c63573ad0e34abbc6b24b6e5d6ff70acb254134729ec0ef
Timestamp: 1703201743 Timestamp [UCT]: 2023-12-21 23:35:43 Age [y:d:h:m:s]: 01:145:17:41:51
Block: 918286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365309 RingCT/type: yes/0
Extra: 018613290735414a390c63573ad0e34abbc6b24b6e5d6ff70acb254134729ec0ef02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64909c77662153c6e983c6134e1f86405b8db6e4c4815e6cb29eac6a84302017 0.600000000000 1375928 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": 918296, "vin": [ { "gen": { "height": 918286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64909c77662153c6e983c6134e1f86405b8db6e4c4815e6cb29eac6a84302017" } } ], "extra": [ 1, 134, 19, 41, 7, 53, 65, 74, 57, 12, 99, 87, 58, 208, 227, 74, 187, 198, 178, 75, 110, 93, 111, 247, 10, 203, 37, 65, 52, 114, 158, 192, 239, 2, 17, 0, 0, 0, 7, 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