Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac1319f0558ea4f6d123f48bd815355909c36ee1cd62dac098f35d9bda3e12a

Tx prefix hash: 66574059b6fd94994ac59b36ac95f110e76507380e5d801f33b438ad1aad2e13
Tx public key: 87e9a9f08703b9c60575d8dabfa4b8e7d532ffdc7a48fb645e3fd68bd5e91814
Timestamp: 1582130133 Timestamp [UCT]: 2020-02-19 16:35:33 Age [y:d:h:m:s]: 04:280:21:07:10
Block: 68335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093104 RingCT/type: yes/0
Extra: 0187e9a9f08703b9c60575d8dabfa4b8e7d532ffdc7a48fb645e3fd68bd5e918140211000000027adf42d3000000000000000000

1 output(s) for total of 364.400180910000 dcy

stealth address amount amount idx
00: 54ea907ac5365f05bb09148ef0a6b81782c0455d34eb9eae7869e8a3734623e9 364.400180910000 125905 of 0

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": 68345, "vin": [ { "gen": { "height": 68335 } } ], "vout": [ { "amount": 364400180910, "target": { "key": "54ea907ac5365f05bb09148ef0a6b81782c0455d34eb9eae7869e8a3734623e9" } } ], "extra": [ 1, 135, 233, 169, 240, 135, 3, 185, 198, 5, 117, 216, 218, 191, 164, 184, 231, 213, 50, 255, 220, 122, 72, 251, 100, 94, 63, 214, 139, 213, 233, 24, 20, 2, 17, 0, 0, 0, 2, 122, 223, 66, 211, 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