Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4398dac048afaac1416df1fcb627c87d83b1c347c078529695f58150137596b3

Tx prefix hash: 55667e4c7c6d1621a5e5ff26bd179e31f9ebb398dd86bcdf5ba066b0d9155f16
Tx public key: 92c945a7ba89ff51b0737a10062ac0c2f59b83dbea92f0df6c98a33b338d1a06
Timestamp: 1732629707 Timestamp [UCT]: 2024-11-26 14:01:47 Age [y:d:h:m:s]: 00:203:21:01:35
Block: 1162162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145452 RingCT/type: yes/0
Extra: 0192c945a7ba89ff51b0737a10062ac0c2f59b83dbea92f0df6c98a33b338d1a06021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c49fc9afc1678f7d07497a47305a98fd2b883a582cea5cb8b05e65c29037555 0.600000000000 1647817 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": 1162172, "vin": [ { "gen": { "height": 1162162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c49fc9afc1678f7d07497a47305a98fd2b883a582cea5cb8b05e65c29037555" } } ], "extra": [ 1, 146, 201, 69, 167, 186, 137, 255, 81, 176, 115, 122, 16, 6, 42, 192, 194, 245, 155, 131, 219, 234, 146, 240, 223, 108, 152, 163, 59, 51, 141, 26, 6, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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