Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59d7f581853f98352b2b1932cea1fad2f2ac6c8b8efc641769e3ed1b41f94d1d

Tx prefix hash: e79425095adf06560fee77d5289449eba760a5aed1318fb431a1740234014c4f
Tx public key: 693c346486d94d57dda6fe59d402657f0fa4441be59d2a45861a6d9a009a1bd0
Timestamp: 1725027774 Timestamp [UCT]: 2024-08-30 14:22:54 Age [y:d:h:m:s]: 00:224:23:23:29
Block: 1099226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160656 RingCT/type: yes/0
Extra: 01693c346486d94d57dda6fe59d402657f0fa4441be59d2a45861a6d9a009a1bd002110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16340d5c85ef0b9e80e923cd99b06abec87b050ae6f4e2e5a45e9fdafad21c41 0.600000000000 1575167 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": 1099236, "vin": [ { "gen": { "height": 1099226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16340d5c85ef0b9e80e923cd99b06abec87b050ae6f4e2e5a45e9fdafad21c41" } } ], "extra": [ 1, 105, 60, 52, 100, 134, 217, 77, 87, 221, 166, 254, 89, 212, 2, 101, 127, 15, 164, 68, 27, 229, 157, 42, 69, 134, 26, 109, 154, 0, 154, 27, 208, 2, 17, 0, 0, 0, 10, 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