Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e86bdd3bbd1defce4f4e7d4a5a542085577eb7f698a8fa1b598196d2fc87babf

Tx prefix hash: 879f4557501822ad90c574e6542c83af6d8b45aaedfd732c2bacf685aee5f110
Tx public key: a92d2920632360e284beffb3cfdfcd7e1681cd1621d01ccf1044a7df4cc2e042
Timestamp: 1703676064 Timestamp [UCT]: 2023-12-27 11:21:04 Age [y:d:h:m:s]: 01:177:22:08:26
Block: 922221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388145 RingCT/type: yes/0
Extra: 01a92d2920632360e284beffb3cfdfcd7e1681cd1621d01ccf1044a7df4cc2e0420211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 306badf61077c6933528dc59f8388a680b865e580f459b1927f3ebfae444e5a9 0.600000000000 1379917 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": 922231, "vin": [ { "gen": { "height": 922221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "306badf61077c6933528dc59f8388a680b865e580f459b1927f3ebfae444e5a9" } } ], "extra": [ 1, 169, 45, 41, 32, 99, 35, 96, 226, 132, 190, 255, 179, 207, 223, 205, 126, 22, 129, 205, 22, 33, 208, 28, 207, 16, 68, 167, 223, 76, 194, 224, 66, 2, 17, 0, 0, 0, 1, 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