Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91fc76b41d0f01f8060c70d41fe2c18f9daec535fcdabde2d90eb2683912ec88

Tx prefix hash: cf4a439a358b18021b9c9259e4c8ab3d08181bbfa27bc19c96376ccd15719ccb
Tx public key: ceb42b41dd1a0252af6b738e7e1ee9e0b50a3acd54e36b45254393cc32363b4e
Timestamp: 1737549375 Timestamp [UCT]: 2025-01-22 12:36:15 Age [y:d:h:m:s]: 00:293:10:20:51
Block: 1202854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207249 RingCT/type: yes/0
Extra: 01ceb42b41dd1a0252af6b738e7e1ee9e0b50a3acd54e36b45254393cc32363b4e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 045afb709bd907b5ebc1673b10b4dfbfa4481628bb0edf16f875e85c8f52fb4d 0.600000000000 1689521 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": 1202864, "vin": [ { "gen": { "height": 1202854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "045afb709bd907b5ebc1673b10b4dfbfa4481628bb0edf16f875e85c8f52fb4d" } } ], "extra": [ 1, 206, 180, 43, 65, 221, 26, 2, 82, 175, 107, 115, 142, 126, 30, 233, 224, 181, 10, 58, 205, 84, 227, 107, 69, 37, 67, 147, 204, 50, 54, 59, 78, 2, 17, 0, 0, 0, 3, 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