Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f01fca7ab54e89f126b26d77732f30690fb410e8877fd512910e4a5816e5da5

Tx prefix hash: cbb42c83123869bb87c4a945d7f966159970f942994065cb5e4532261a5a60db
Tx public key: bfd28e9e60560425adc1db727de07de9d449913dea992f329d5a008c98c2f07e
Timestamp: 1721961176 Timestamp [UCT]: 2024-07-26 02:32:56 Age [y:d:h:m:s]: 00:325:20:09:07
Block: 1073813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232728 RingCT/type: yes/0
Extra: 01bfd28e9e60560425adc1db727de07de9d449913dea992f329d5a008c98c2f07e02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d7093d96da4c8f9fa78d610c9ab44ea59e976bfc6cb91eb6e11368b52c949b6 0.600000000000 1546320 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": 1073823, "vin": [ { "gen": { "height": 1073813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d7093d96da4c8f9fa78d610c9ab44ea59e976bfc6cb91eb6e11368b52c949b6" } } ], "extra": [ 1, 191, 210, 142, 158, 96, 86, 4, 37, 173, 193, 219, 114, 125, 224, 125, 233, 212, 73, 145, 61, 234, 153, 47, 50, 157, 90, 0, 140, 152, 194, 240, 126, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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