Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6088687ac4724920bd4249c419b351f72df67cf1b305ecf5e964e55e3c40338

Tx prefix hash: 7ed914d91230f4a0d126cb7db567841fc5f4b0112bb2c46697b5e563619960a5
Tx public key: 0e2493cb34df2bf7c304c8631db8e00b8d3e61a3634a09e10122ac6b9b638f67
Timestamp: 1746222677 Timestamp [UCT]: 2025-05-02 21:51:17 Age [y:d:h:m:s]: 00:199:01:13:01
Block: 1274434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139970 RingCT/type: yes/0
Extra: 010e2493cb34df2bf7c304c8631db8e00b8d3e61a3634a09e10122ac6b9b638f670211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecc4abee42b3455e6d9a692f9a52800e790c10ef9cf63029aa20b12ca1ea86eb 0.600000000000 1761729 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": 1274444, "vin": [ { "gen": { "height": 1274434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecc4abee42b3455e6d9a692f9a52800e790c10ef9cf63029aa20b12ca1ea86eb" } } ], "extra": [ 1, 14, 36, 147, 203, 52, 223, 43, 247, 195, 4, 200, 99, 29, 184, 224, 11, 141, 62, 97, 163, 99, 74, 9, 225, 1, 34, 172, 107, 155, 99, 143, 103, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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