Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c4731812d30a10b59590b205879b3b91d5c03c14987c87feb88a3ea54377483

Tx prefix hash: 039c53ebb32b00ca77d7b281cf2833783527824d4a3821d6b7583527b00669e4
Tx public key: 0ad9f29fe952ebf55f1b9b0b40a3ef58966ff40b0566cf5c3bb30b266d4387c2
Timestamp: 1735459339 Timestamp [UCT]: 2024-12-29 08:02:19 Age [y:d:h:m:s]: 00:325:07:31:07
Block: 1185585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230024 RingCT/type: yes/0
Extra: 010ad9f29fe952ebf55f1b9b0b40a3ef58966ff40b0566cf5c3bb30b266d4387c2021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d7c5fb014eb77a61678252e4587957aa24adde1c193df23c4557191bac2efd7 0.600000000000 1672060 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": 1185595, "vin": [ { "gen": { "height": 1185585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d7c5fb014eb77a61678252e4587957aa24adde1c193df23c4557191bac2efd7" } } ], "extra": [ 1, 10, 217, 242, 159, 233, 82, 235, 245, 95, 27, 155, 11, 64, 163, 239, 88, 150, 111, 244, 11, 5, 102, 207, 92, 59, 179, 11, 38, 109, 67, 135, 194, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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