Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cfe45b282854e9cb758e974d4ff26d493d9a0846f85581174cc6ba91a0a0214

Tx prefix hash: 105a6f3df95c4b33d6c554bf318d59f9f37c6a51159185b17a070e757a28f6de
Tx public key: bf10ee0e741572d5fcd435022fdf7b7c86cf6ffc533ae8e2b5f0fec6265ec751
Timestamp: 1714021102 Timestamp [UCT]: 2024-04-25 04:58:22 Age [y:d:h:m:s]: 00:306:02:20:03
Block: 1007981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218791 RingCT/type: yes/0
Extra: 01bf10ee0e741572d5fcd435022fdf7b7c86cf6ffc533ae8e2b5f0fec6265ec75102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1be7b507c832242d8bbd19e335edcaee99ac18faab1c9c5eaa6fa1c71ca65e0d 0.600000000000 1469447 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": 1007991, "vin": [ { "gen": { "height": 1007981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1be7b507c832242d8bbd19e335edcaee99ac18faab1c9c5eaa6fa1c71ca65e0d" } } ], "extra": [ 1, 191, 16, 238, 14, 116, 21, 114, 213, 252, 212, 53, 2, 47, 223, 123, 124, 134, 207, 111, 252, 83, 58, 232, 226, 181, 240, 254, 198, 38, 94, 199, 81, 2, 17, 0, 0, 0, 4, 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