Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06034093a4c712b70bfe56726309fac6ce2c18d14541af20dbf5638f7e7a7ad5

Tx prefix hash: 4a5101281c5df9d3a3fdd7f84d633d9f8f21ccebe02bab15b95be94705fd453d
Tx public key: 0696c9e8f3c71abc7b76d475e78d782044c9803d992ab6f9db87e425597e297f
Timestamp: 1764479443 Timestamp [UCT]: 2025-11-30 05:10:43 Age [y:d:h:m:s]: 00:063:07:15:28
Block: 1423181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45138 RingCT/type: yes/0
Extra: 010696c9e8f3c71abc7b76d475e78d782044c9803d992ab6f9db87e425597e297f02110000000143b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f8331775529a1ed5c1d1fe66b1702e995eff9fa8e068f600a06ff62750afa9b 0.600000000000 1911784 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": 1423191, "vin": [ { "gen": { "height": 1423181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f8331775529a1ed5c1d1fe66b1702e995eff9fa8e068f600a06ff62750afa9b" } } ], "extra": [ 1, 6, 150, 201, 232, 243, 199, 26, 188, 123, 118, 212, 117, 231, 141, 120, 32, 68, 201, 128, 61, 153, 42, 182, 249, 219, 135, 228, 37, 89, 126, 41, 127, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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