Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f554150cec30f8a17ec17c7614f0175ffbb05e40ca3c0e30e36c1e1def1584d5

Tx prefix hash: ac648e680fe6b7c3b5e02de7fa2d79aa5fc8c9ae9e4e13c921e3520036d8df31
Tx public key: 42d32ef9104c0e6a7630778a72a0013e3cd9b428a60f96e8e26e270dd0712509
Timestamp: 1736997020 Timestamp [UCT]: 2025-01-16 03:10:20 Age [y:d:h:m:s]: 00:156:19:49:58
Block: 1198317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111738 RingCT/type: yes/0
Extra: 0142d32ef9104c0e6a7630778a72a0013e3cd9b428a60f96e8e26e270dd0712509021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 346b59d5fc1ddd767348dc3957d44523d37da0fcfcb992e096a71fcd86af1876 0.600000000000 1684940 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": 1198327, "vin": [ { "gen": { "height": 1198317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "346b59d5fc1ddd767348dc3957d44523d37da0fcfcb992e096a71fcd86af1876" } } ], "extra": [ 1, 66, 211, 46, 249, 16, 76, 14, 106, 118, 48, 119, 138, 114, 160, 1, 62, 60, 217, 180, 40, 166, 15, 150, 232, 226, 110, 39, 13, 208, 113, 37, 9, 2, 17, 0, 0, 0, 5, 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