Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0617ef0f7e5ca3d1243f7d3e7d342f8c8207eaad6319c168db21d7e7987e26ae

Tx prefix hash: 9e51749a8e52924c6b80a1418defddcce678458fb9fa214735f64beb3414a4ff
Tx public key: e1ebf19881870be82ca1dc4b3ba67d67e1136d726aa47a5272910ef19e9005fb
Timestamp: 1722111951 Timestamp [UCT]: 2024-07-27 20:25:51 Age [y:d:h:m:s]: 00:258:14:09:00
Block: 1075068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184717 RingCT/type: yes/0
Extra: 01e1ebf19881870be82ca1dc4b3ba67d67e1136d726aa47a5272910ef19e9005fb021100000011e914dd15000000000000000000

1 output(s) for total of 0.600060000000 dcy

stealth address amount amount idx
00: 624540299ad4a13dec072c0634e550b5da19957336fbd22eabc298aa0815df7b 0.600060000000 1547589 of 0

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": 1075078, "vin": [ { "gen": { "height": 1075068 } } ], "vout": [ { "amount": 600060000, "target": { "key": "624540299ad4a13dec072c0634e550b5da19957336fbd22eabc298aa0815df7b" } } ], "extra": [ 1, 225, 235, 241, 152, 129, 135, 11, 232, 44, 161, 220, 75, 59, 166, 125, 103, 225, 19, 109, 114, 106, 164, 122, 82, 114, 145, 14, 241, 158, 144, 5, 251, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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