Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e98e478a8699bbc617ad907ae07654cd149b1cc0a9f428e52b8e94073e50272b

Tx prefix hash: 158a0588f180cabe633308d78b4a9793efa24aa3ef70b72b75791edbfa415b0d
Tx public key: 9ec0e1cc89f74ae906c3729e1cde46d85f7aa0000f95e8a7640e6ef0b5e3a8e2
Timestamp: 1702884182 Timestamp [UCT]: 2023-12-18 07:23:02 Age [y:d:h:m:s]: 01:338:16:29:11
Block: 915657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500910 RingCT/type: yes/0
Extra: 019ec0e1cc89f74ae906c3729e1cde46d85f7aa0000f95e8a7640e6ef0b5e3a8e2021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a1537614fbd2db413f6209dc0eec468b86aeee12d6a975fb990c3c0d04e474b 0.600000000000 1373053 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": 915667, "vin": [ { "gen": { "height": 915657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a1537614fbd2db413f6209dc0eec468b86aeee12d6a975fb990c3c0d04e474b" } } ], "extra": [ 1, 158, 192, 225, 204, 137, 247, 74, 233, 6, 195, 114, 158, 28, 222, 70, 216, 95, 122, 160, 0, 15, 149, 232, 167, 100, 14, 110, 240, 181, 227, 168, 226, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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