Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 415af08df65b2a7a2ee6ad303dc61a9cdfba7dddc435c5905f1b427cb60b78fd

Tx prefix hash: 6bbccda3b7511f0544388b303e546b08f5d272eb9824f87b5f001f776b9fcdbc
Tx public key: 715ef946df04b188ea1afff67ecac53f976480536d5c29594fc852083ebc01a4
Timestamp: 1720310280 Timestamp [UCT]: 2024-07-06 23:58:00 Age [y:d:h:m:s]: 00:231:14:36:28
Block: 1060121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165435 RingCT/type: yes/0
Extra: 01715ef946df04b188ea1afff67ecac53f976480536d5c29594fc852083ebc01a4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fe5aa492d0f577a89c1b725a5df8fc05f11a417427170f660aeb4fba6ca7ecb 0.600000000000 1530592 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": 1060131, "vin": [ { "gen": { "height": 1060121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fe5aa492d0f577a89c1b725a5df8fc05f11a417427170f660aeb4fba6ca7ecb" } } ], "extra": [ 1, 113, 94, 249, 70, 223, 4, 177, 136, 234, 26, 255, 246, 126, 202, 197, 63, 151, 100, 128, 83, 109, 92, 41, 89, 79, 200, 82, 8, 62, 188, 1, 164, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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