Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c66f4cebcd1a613939b0dbd158798d558dcf260910d9aabed53b0b8fca196479

Tx prefix hash: c4b959bedae76f44260bcee4ffa9e652c323a2cac9906cfce73375462bc2a2e7
Tx public key: 4dd03fb0a4e3c1010ead1a6f024c595c4ae1fb1610cda3e9c9caa4f8b2b884dc
Timestamp: 1733699442 Timestamp [UCT]: 2024-12-08 23:10:42 Age [y:d:h:m:s]: 00:191:03:15:53
Block: 1171046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136310 RingCT/type: yes/0
Extra: 014dd03fb0a4e3c1010ead1a6f024c595c4ae1fb1610cda3e9c9caa4f8b2b884dc02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7e9bc1c82cc0a978603ad542ddd8ac85c3b283e7022417d89bacef4f9358b60 0.600000000000 1656781 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": 1171056, "vin": [ { "gen": { "height": 1171046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7e9bc1c82cc0a978603ad542ddd8ac85c3b283e7022417d89bacef4f9358b60" } } ], "extra": [ 1, 77, 208, 63, 176, 164, 227, 193, 1, 14, 173, 26, 111, 2, 76, 89, 92, 74, 225, 251, 22, 16, 205, 163, 233, 201, 202, 164, 248, 178, 184, 132, 220, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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