Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d1466bab1b5ded21c82bb84b59d75ea46292b35169a30aa3f3b31e56c55ddd5

Tx prefix hash: 597531c970a04347da1f07bf813a9d94c29777507462d211c25e3593ad0f5221
Tx public key: 5d61f572982d7b5735c85706d9a7e23cb2edaa77822953ea914e4ec8d50dff05
Timestamp: 1703489841 Timestamp [UCT]: 2023-12-25 07:37:21 Age [y:d:h:m:s]: 01:321:17:36:06
Block: 920676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488776 RingCT/type: yes/0
Extra: 015d61f572982d7b5735c85706d9a7e23cb2edaa77822953ea914e4ec8d50dff050211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32cfbcf5fbd0ce04ec3da56f0d0fd8cd074a79372c4a4e9ed68aff19dca6ff3e 0.600000000000 1378358 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": 920686, "vin": [ { "gen": { "height": 920676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32cfbcf5fbd0ce04ec3da56f0d0fd8cd074a79372c4a4e9ed68aff19dca6ff3e" } } ], "extra": [ 1, 93, 97, 245, 114, 152, 45, 123, 87, 53, 200, 87, 6, 217, 167, 226, 60, 178, 237, 170, 119, 130, 41, 83, 234, 145, 78, 78, 200, 213, 13, 255, 5, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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