Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e190f15d60c8d5017acb768a7f7685a6bff709b08f596eb01b0bdd2335392efe

Tx prefix hash: a4aa710aa12214a4c6c1260c0009ea1d2bc181e0be01b57b263984f2be75c00c
Tx public key: 9b75932f3484ff9316ab16b94af31ba632af343c4b9747a9527c860855f0aca4
Timestamp: 1723546824 Timestamp [UCT]: 2024-08-13 11:00:24 Age [y:d:h:m:s]: 00:238:17:22:07
Block: 1086963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170491 RingCT/type: yes/0
Extra: 019b75932f3484ff9316ab16b94af31ba632af343c4b9747a9527c860855f0aca402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d7fb49ac83a4e46aea1de6fc13db4272ed7db5da83081e818ef2aa668b99dc5 0.600000000000 1561562 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": 1086973, "vin": [ { "gen": { "height": 1086963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d7fb49ac83a4e46aea1de6fc13db4272ed7db5da83081e818ef2aa668b99dc5" } } ], "extra": [ 1, 155, 117, 147, 47, 52, 132, 255, 147, 22, 171, 22, 185, 74, 243, 27, 166, 50, 175, 52, 60, 75, 151, 71, 169, 82, 124, 134, 8, 85, 240, 172, 164, 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