Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27619abbd11e3620c23afce701cdd8dd9f3501b0b4db4d11c1bda020d8398189

Tx prefix hash: 406b5a95eac192cbd22b1712301a9ee074019f53ddb705cfebab16b24a4b5638
Tx public key: de9756c88a3b67fc9e5adf25d36310c3c5288a04e68463465bc5e5b7b3cce9d7
Timestamp: 1723928735 Timestamp [UCT]: 2024-08-17 21:05:35 Age [y:d:h:m:s]: 00:213:22:53:04
Block: 1090140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152787 RingCT/type: yes/0
Extra: 01de9756c88a3b67fc9e5adf25d36310c3c5288a04e68463465bc5e5b7b3cce9d702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae8e8efea44eea5d087231ae47e57ef7e571e95a24d5dbdc93893f710cef76be 0.600000000000 1564763 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": 1090150, "vin": [ { "gen": { "height": 1090140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae8e8efea44eea5d087231ae47e57ef7e571e95a24d5dbdc93893f710cef76be" } } ], "extra": [ 1, 222, 151, 86, 200, 138, 59, 103, 252, 158, 90, 223, 37, 211, 99, 16, 195, 197, 40, 138, 4, 230, 132, 99, 70, 91, 197, 229, 183, 179, 204, 233, 215, 2, 17, 0, 0, 0, 1, 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