Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8024ba374d68abfd1155d56c17dd4d5f4669322922fe3671af9c762725b5a86

Tx prefix hash: e4de70f45ad94d0efc1799e290f441c8e17763abbe38ab827b545d9f2f5675d7
Tx public key: 38a8d5044cffe8791e76a3acb684a537ce3d69cd145ec4e421432c5df5115b75
Timestamp: 1708144270 Timestamp [UCT]: 2024-02-17 04:31:10 Age [y:d:h:m:s]: 01:038:09:10:42
Block: 959264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288454 RingCT/type: yes/0
Extra: 0138a8d5044cffe8791e76a3acb684a537ce3d69cd145ec4e421432c5df5115b750211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b677a1f0e8c2ff68cafd16b945ecf61a9f48dce43204be383fbffd7f4f4c8f95 0.600000000000 1418795 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": 959274, "vin": [ { "gen": { "height": 959264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b677a1f0e8c2ff68cafd16b945ecf61a9f48dce43204be383fbffd7f4f4c8f95" } } ], "extra": [ 1, 56, 168, 213, 4, 76, 255, 232, 121, 30, 118, 163, 172, 182, 132, 165, 55, 206, 61, 105, 205, 20, 94, 196, 228, 33, 67, 44, 93, 245, 17, 91, 117, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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