Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24b702e8fd6f5303c9ea05713d9e81af0a774234cb30748a54ca3691339a9182

Tx prefix hash: 2c8ce936f648832db73720386dcda15f59e5dc682d0b18401f931bfdaa7f469c
Tx public key: f4f759e2a65143c963a4a783e83ded680c9de0ce493549565d1f66fae5b74185
Timestamp: 1704118952 Timestamp [UCT]: 2024-01-01 14:22:32 Age [y:d:h:m:s]: 01:090:20:22:48
Block: 925888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326030 RingCT/type: yes/0
Extra: 01f4f759e2a65143c963a4a783e83ded680c9de0ce493549565d1f66fae5b741850211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65697c57a85cbbd4ae785548a6de98938b2710c781cd49e69abb73b414b7e8e2 0.600000000000 1383658 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": 925898, "vin": [ { "gen": { "height": 925888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65697c57a85cbbd4ae785548a6de98938b2710c781cd49e69abb73b414b7e8e2" } } ], "extra": [ 1, 244, 247, 89, 226, 166, 81, 67, 201, 99, 164, 167, 131, 232, 61, 237, 104, 12, 157, 224, 206, 73, 53, 73, 86, 93, 31, 102, 250, 229, 183, 65, 133, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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