Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 021143568885942581d7243c548b9c924fb5f7d41bf76a4c64ab97cddf60e577

Tx prefix hash: 3e068b4a83e359e46875057c5a86ebb9be2263e043ddd3ec24ba1e17d9e4d376
Tx public key: 04199b564ba4b0e9db585c818e4af4bd79bbfb1cd44b7def9a348a8ba2621ac6
Timestamp: 1728694533 Timestamp [UCT]: 2024-10-12 00:55:33 Age [y:d:h:m:s]: 00:078:16:52:35
Block: 1129638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56240 RingCT/type: yes/0
Extra: 0104199b564ba4b0e9db585c818e4af4bd79bbfb1cd44b7def9a348a8ba2621ac6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53a19a516679227bbd6581c0fe86d6ad818ddffcd2da20b7d29246a206aab9d7 0.600000000000 1612471 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": 1129648, "vin": [ { "gen": { "height": 1129638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53a19a516679227bbd6581c0fe86d6ad818ddffcd2da20b7d29246a206aab9d7" } } ], "extra": [ 1, 4, 25, 155, 86, 75, 164, 176, 233, 219, 88, 92, 129, 142, 74, 244, 189, 121, 187, 251, 28, 212, 75, 125, 239, 154, 52, 138, 139, 162, 98, 26, 198, 2, 17, 0, 0, 0, 3, 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