Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 283863a172d9ae539381295b7b4c2d33c6cde0b92c1c74c56a0ee118b6b70392

Tx prefix hash: 877cbc8f6e80469ef9b15ed74f8e6d99ed3128b176bda656a2b485d1ca85e0a5
Tx public key: c84912ac3889c04ab9ac43b8d2552ecf252b55579f55a9b56047c68da025df3a
Timestamp: 1723520394 Timestamp [UCT]: 2024-08-13 03:39:54 Age [y:d:h:m:s]: 00:240:04:03:57
Block: 1086737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171538 RingCT/type: yes/0
Extra: 01c84912ac3889c04ab9ac43b8d2552ecf252b55579f55a9b56047c68da025df3a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd6cba91c243597c26624b300f24ebeb80800d061de291cf0dea1868176076e1 0.600000000000 1561336 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": 1086747, "vin": [ { "gen": { "height": 1086737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd6cba91c243597c26624b300f24ebeb80800d061de291cf0dea1868176076e1" } } ], "extra": [ 1, 200, 73, 18, 172, 56, 137, 192, 74, 185, 172, 67, 184, 210, 85, 46, 207, 37, 43, 85, 87, 159, 85, 169, 181, 96, 71, 198, 141, 160, 37, 223, 58, 2, 17, 0, 0, 0, 2, 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