Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09cd1ad8fc0f42b2af33b3fae203b3327b4b8d15b87a77acc731d16636ee6a24

Tx prefix hash: f07eca267591a171f182cfd80c7709a0602bad4e5bd7b04cec1de112f2d48aa0
Tx public key: 4767b5be314adbbcb94e185de686810c772b945e9ec91769ec1c1db8bbce9e66
Timestamp: 1722535427 Timestamp [UCT]: 2024-08-01 18:03:47 Age [y:d:h:m:s]: 00:115:04:54:44
Block: 1078570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82429 RingCT/type: yes/0
Extra: 014767b5be314adbbcb94e185de686810c772b945e9ec91769ec1c1db8bbce9e6602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee58f3290aabf488ae46e41bb5a2c196a4ad89339a2e2b056807cbfb86538de9 0.600000000000 1551165 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": 1078580, "vin": [ { "gen": { "height": 1078570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee58f3290aabf488ae46e41bb5a2c196a4ad89339a2e2b056807cbfb86538de9" } } ], "extra": [ 1, 71, 103, 181, 190, 49, 74, 219, 188, 185, 78, 24, 93, 230, 134, 129, 12, 119, 43, 148, 94, 158, 201, 23, 105, 236, 28, 29, 184, 187, 206, 158, 102, 2, 17, 0, 0, 0, 5, 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