Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e89a2430894ccffea0a0cda8db34b80ab1ce2eb46547047f1017cf5f220cd91

Tx prefix hash: 7d0ae9eaf746377ff6cff74816f2efe40a4ed5178e94829cb2c3ef9ed4360bc1
Tx public key: a055b5c83d0c36f87eaf20599722dd10a158d1e2bfb5b51b8912afbc58d9a6c9
Timestamp: 1717351759 Timestamp [UCT]: 2024-06-02 18:09:19 Age [y:d:h:m:s]: 01:017:11:34:14
Block: 1035611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273256 RingCT/type: yes/0
Extra: 01a055b5c83d0c36f87eaf20599722dd10a158d1e2bfb5b51b8912afbc58d9a6c9021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 791462232f7ad7ed6ea8545da9f5225d740920a57a7c8d0d1c9bdf05d922ffac 0.600000000000 1504132 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": 1035621, "vin": [ { "gen": { "height": 1035611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "791462232f7ad7ed6ea8545da9f5225d740920a57a7c8d0d1c9bdf05d922ffac" } } ], "extra": [ 1, 160, 85, 181, 200, 61, 12, 54, 248, 126, 175, 32, 89, 151, 34, 221, 16, 161, 88, 209, 226, 191, 181, 181, 27, 137, 18, 175, 188, 88, 217, 166, 201, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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