Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf506a8ea94ee6405b9e9ea61ada02896a3b3c9b05dcdee5298789944c9b6691

Tx prefix hash: 91ebac3d943016751f7c2deb8768df7173d0732987fafdc974cd12d69e21cc0c
Tx public key: ac1d9fb1ac771151da51c8ee5b5055059f7706bb1bed4fdc7e51e935e8abee19
Timestamp: 1707936089 Timestamp [UCT]: 2024-02-14 18:41:29 Age [y:d:h:m:s]: 01:040:20:09:35
Block: 957530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290210 RingCT/type: yes/0
Extra: 01ac1d9fb1ac771151da51c8ee5b5055059f7706bb1bed4fdc7e51e935e8abee190211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73837bc41af950b273c178c67f6317f3f2f0075b62bc4be5e64cff1e717bba01 0.600000000000 1416848 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": 957540, "vin": [ { "gen": { "height": 957530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73837bc41af950b273c178c67f6317f3f2f0075b62bc4be5e64cff1e717bba01" } } ], "extra": [ 1, 172, 29, 159, 177, 172, 119, 17, 81, 218, 81, 200, 238, 91, 80, 85, 5, 159, 119, 6, 187, 27, 237, 79, 220, 126, 81, 233, 53, 232, 171, 238, 25, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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