Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10414757d842766480229aa5ff0c9a9a2ca4b752cdc1eb3717eaaf57b9487009

Tx prefix hash: d5b2d7dfa9a281e985300cc92f4160962775ce2f3dc6c30783e8a572010f00c8
Tx public key: f0cfff1e679c1a959728f1a1c59302a1e9769b664170d41c2ad2997e8e6b083c
Timestamp: 1737852345 Timestamp [UCT]: 2025-01-26 00:45:45 Age [y:d:h:m:s]: 00:047:22:37:55
Block: 1205359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34086 RingCT/type: yes/0
Extra: 01f0cfff1e679c1a959728f1a1c59302a1e9769b664170d41c2ad2997e8e6b083c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 976b67b8305eb06104796abd456a58939081a13f5a3e33242a9e6312506f33dc 0.600000000000 1692056 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": 1205369, "vin": [ { "gen": { "height": 1205359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "976b67b8305eb06104796abd456a58939081a13f5a3e33242a9e6312506f33dc" } } ], "extra": [ 1, 240, 207, 255, 30, 103, 156, 26, 149, 151, 40, 241, 161, 197, 147, 2, 161, 233, 118, 155, 102, 65, 112, 212, 28, 42, 210, 153, 126, 142, 107, 8, 60, 2, 17, 0, 0, 0, 2, 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