Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc9074ea62b15ebf6ad0291ddd3f08439fe7bbab8a61a2c363b40b4a33c1d8b8

Tx prefix hash: 4df77aa6acd9c41eba9a5fa779eafbdabf7b810ed10ad49652fb6ea41cd64d5c
Tx public key: f65d5066198470a755dbf626ea677affb86933214ec7835ea1d3c71f9bfe9118
Timestamp: 1703639672 Timestamp [UCT]: 2023-12-27 01:14:32 Age [y:d:h:m:s]: 01:315:02:55:05
Block: 921921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484026 RingCT/type: yes/0
Extra: 01f65d5066198470a755dbf626ea677affb86933214ec7835ea1d3c71f9bfe911802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fbfcac041f137a7d3347de8ddc7e60fca77826eba69831a4d86b6b70d6e8d3d 0.600000000000 1379615 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": 921931, "vin": [ { "gen": { "height": 921921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fbfcac041f137a7d3347de8ddc7e60fca77826eba69831a4d86b6b70d6e8d3d" } } ], "extra": [ 1, 246, 93, 80, 102, 25, 132, 112, 167, 85, 219, 246, 38, 234, 103, 122, 255, 184, 105, 51, 33, 78, 199, 131, 94, 161, 211, 199, 31, 155, 254, 145, 24, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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