Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a92e9ba02dbcdd77f77db7f38b054c4ae49de554346be4bdce5caec4e9c2c58

Tx prefix hash: 4dca6140e2838f95cd465bc835add5c865821390da1740885c34a479fcc4e121
Tx public key: 7134bfac711a6b93d2aa5aa7e2e851b11ec2cac0af3d51a2e29cf78e2a0043ae
Timestamp: 1739273842 Timestamp [UCT]: 2025-02-11 11:37:22 Age [y:d:h:m:s]: 00:345:08:35:01
Block: 1216908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244528 RingCT/type: yes/0
Extra: 017134bfac711a6b93d2aa5aa7e2e851b11ec2cac0af3d51a2e29cf78e2a0043ae021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c6f9ab4244a4f4779cd193f63f2565d3b69387bf615ee6ecfc69b5f316805e1 0.600000000000 1703717 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": 1216918, "vin": [ { "gen": { "height": 1216908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c6f9ab4244a4f4779cd193f63f2565d3b69387bf615ee6ecfc69b5f316805e1" } } ], "extra": [ 1, 113, 52, 191, 172, 113, 26, 107, 147, 210, 170, 90, 167, 226, 232, 81, 177, 30, 194, 202, 192, 175, 61, 81, 162, 226, 156, 247, 142, 42, 0, 67, 174, 2, 17, 0, 0, 0, 6, 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