Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8500a41330aade99a1ce107d9f36f35920a3af66e71249e4a509af01642a544

Tx prefix hash: 7b14756b77ec407a06f492fd2cbe81f3bc8e7118556985831271d22c6deea236
Tx public key: c961aefca68553dffb01c4c76a2a76ce2c894e96c37a0b48c643fdf371225680
Timestamp: 1727932720 Timestamp [UCT]: 2024-10-03 05:18:40 Age [y:d:h:m:s]: 00:240:22:05:04
Block: 1123319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172029 RingCT/type: yes/0
Extra: 01c961aefca68553dffb01c4c76a2a76ce2c894e96c37a0b48c643fdf371225680021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccafa9c96602b90f2e684d1bdd30fe8f7b138b5ae5e3c0605e869c94d888c8ce 0.600000000000 1605852 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": 1123329, "vin": [ { "gen": { "height": 1123319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccafa9c96602b90f2e684d1bdd30fe8f7b138b5ae5e3c0605e869c94d888c8ce" } } ], "extra": [ 1, 201, 97, 174, 252, 166, 133, 83, 223, 251, 1, 196, 199, 106, 42, 118, 206, 44, 137, 78, 150, 195, 122, 11, 72, 198, 67, 253, 243, 113, 34, 86, 128, 2, 17, 0, 0, 0, 4, 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