Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d66a024a2df1d60f767295b3d271f76ebe0761a994e9ffb830e13d7193292290

Tx prefix hash: 6224b8a98b2e478d8ff8a94dfa42605fd465a09f2dfc411f929a73fcce65de6b
Tx public key: 76f39c8ec3f278f6e5daac32e8b1e7bffb52597724ed70b9e0a8a3734e37fadc
Timestamp: 1712217964 Timestamp [UCT]: 2024-04-04 08:06:04 Age [y:d:h:m:s]: 00:279:20:53:52
Block: 993006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200361 RingCT/type: yes/0
Extra: 0176f39c8ec3f278f6e5daac32e8b1e7bffb52597724ed70b9e0a8a3734e37fadc02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9b1eaa4437623968f222ad9844b624f7395d5cebbfb5e3019987899e62f39f4 0.600000000000 1453384 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": 993016, "vin": [ { "gen": { "height": 993006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9b1eaa4437623968f222ad9844b624f7395d5cebbfb5e3019987899e62f39f4" } } ], "extra": [ 1, 118, 243, 156, 142, 195, 242, 120, 246, 229, 218, 172, 50, 232, 177, 231, 191, 251, 82, 89, 119, 36, 237, 112, 185, 224, 168, 163, 115, 78, 55, 250, 220, 2, 17, 0, 0, 0, 1, 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