Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81cbbb370b2110d1891da566f5d6f0d2a8c0f583dec8e78ca5266cbc330cdb09

Tx prefix hash: 80e682e3bf14829f4f9db4dd900994e04fa258f20ef2e102c972beec20c7e9d6
Tx public key: 7d9c1ae9ffbe011bf549470a809958e96603c1c8792e8144b2a423f0fb187e24
Timestamp: 1738522569 Timestamp [UCT]: 2025-02-02 18:56:09 Age [y:d:h:m:s]: 00:333:10:48:43
Block: 1210680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236145 RingCT/type: yes/0
Extra: 017d9c1ae9ffbe011bf549470a809958e96603c1c8792e8144b2a423f0fb187e240211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69db7dcd7ccc1c94f99454a5aef76bed9f5619bb4ad393154ab20a9bb2f0525e 0.600000000000 1697433 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": 1210690, "vin": [ { "gen": { "height": 1210680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69db7dcd7ccc1c94f99454a5aef76bed9f5619bb4ad393154ab20a9bb2f0525e" } } ], "extra": [ 1, 125, 156, 26, 233, 255, 190, 1, 27, 245, 73, 71, 10, 128, 153, 88, 233, 102, 3, 193, 200, 121, 46, 129, 68, 178, 164, 35, 240, 251, 24, 126, 36, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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