Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1aecd3537c49c462f3289dcebfda796fd5eaf8dd81846e8ed8dfd1b12db8ca57

Tx prefix hash: 65d1d57041a08ae64d1b868b36ed058a830b2ce4fd1f5bae201242d7bf0803d8
Tx public key: 259bf66111f2131d14ab4896db81fa945660fd5b91cbf4c24085e804d17363e5
Timestamp: 1721463032 Timestamp [UCT]: 2024-07-20 08:10:32 Age [y:d:h:m:s]: 00:285:19:21:38
Block: 1069678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204207 RingCT/type: yes/0
Extra: 01259bf66111f2131d14ab4896db81fa945660fd5b91cbf4c24085e804d17363e502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 843c3f79e2289a0d9c72289032bf58e4d406c8255d63513dc9b0808ebcc3ebf2 0.600000000000 1541207 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": 1069688, "vin": [ { "gen": { "height": 1069678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "843c3f79e2289a0d9c72289032bf58e4d406c8255d63513dc9b0808ebcc3ebf2" } } ], "extra": [ 1, 37, 155, 246, 97, 17, 242, 19, 29, 20, 171, 72, 150, 219, 129, 250, 148, 86, 96, 253, 91, 145, 203, 244, 194, 64, 133, 232, 4, 209, 115, 99, 229, 2, 17, 0, 0, 0, 6, 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