Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb874b732735c86b15c9f15f2f0d9b9b1eb7c28abc539142baaf13e00d17250d

Tx prefix hash: 5c6e22008ca55dfc697a2fd7ff4a32466da4803f31b80e6f6031112710a7c77e
Tx public key: 41dc28d251a58b40f94246bfde0727fec52932e5a81ac54c0ff5bc86d28d6667
Timestamp: 1723752833 Timestamp [UCT]: 2024-08-15 20:13:53 Age [y:d:h:m:s]: 00:243:05:47:14
Block: 1088669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173735 RingCT/type: yes/0
Extra: 0141dc28d251a58b40f94246bfde0727fec52932e5a81ac54c0ff5bc86d28d6667021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e39156b3686e11ee6df472efe6e3a0a3e34e3994ea58c850406789d8a22f87a6 0.600000000000 1563286 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": 1088679, "vin": [ { "gen": { "height": 1088669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e39156b3686e11ee6df472efe6e3a0a3e34e3994ea58c850406789d8a22f87a6" } } ], "extra": [ 1, 65, 220, 40, 210, 81, 165, 139, 64, 249, 66, 70, 191, 222, 7, 39, 254, 197, 41, 50, 229, 168, 26, 197, 76, 15, 245, 188, 134, 210, 141, 102, 103, 2, 17, 0, 0, 0, 1, 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