Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da549677340a1e50dc1e15f60456935c284f0844c6aa85000c33047c2487516d

Tx prefix hash: 35199d9444e713779097ca6b9e31cd125f1187696f6b797ab409fe9c5e9c6887
Tx public key: 2cbd8a4fce6fac97cc6cdfd4c60fa8d2b0d1d990412e758d2314da0117690fc4
Timestamp: 1714427002 Timestamp [UCT]: 2024-04-29 21:43:22 Age [y:d:h:m:s]: 00:208:04:05:38
Block: 1011346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149030 RingCT/type: yes/0
Extra: 012cbd8a4fce6fac97cc6cdfd4c60fa8d2b0d1d990412e758d2314da0117690fc40211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb0e8cfba9009c90626516f5638224e638d9c62d4a4587277fccadb28c4e119c 0.600000000000 1473552 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": 1011356, "vin": [ { "gen": { "height": 1011346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb0e8cfba9009c90626516f5638224e638d9c62d4a4587277fccadb28c4e119c" } } ], "extra": [ 1, 44, 189, 138, 79, 206, 111, 172, 151, 204, 108, 223, 212, 198, 15, 168, 210, 176, 209, 217, 144, 65, 46, 117, 141, 35, 20, 218, 1, 23, 105, 15, 196, 2, 17, 0, 0, 0, 2, 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