Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d422eef5021e3868209f94c6cbb525f087def235526d7c6b0d30373cdf4e398b

Tx prefix hash: 9c01648c953618106a1be8cc1ab9426cde3c783a28bb8e4c375a5f805f17e3c1
Tx public key: 960cdfb037bcd5ed1c39c585ab7295131d442b8df53627393eec25a758b2475e
Timestamp: 1717109058 Timestamp [UCT]: 2024-05-30 22:44:18 Age [y:d:h:m:s]: 00:308:13:04:37
Block: 1033582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220517 RingCT/type: yes/0
Extra: 01960cdfb037bcd5ed1c39c585ab7295131d442b8df53627393eec25a758b2475e02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56b7d8a6c0769b77690cce5503ee1348a5ab01e8e13e0c67d5671146f18351ad 0.600000000000 1502053 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": 1033592, "vin": [ { "gen": { "height": 1033582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56b7d8a6c0769b77690cce5503ee1348a5ab01e8e13e0c67d5671146f18351ad" } } ], "extra": [ 1, 150, 12, 223, 176, 55, 188, 213, 237, 28, 57, 197, 133, 171, 114, 149, 19, 29, 68, 43, 141, 245, 54, 39, 57, 62, 236, 37, 167, 88, 178, 71, 94, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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