Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 148df1e00f1542e4a39336bebaf942b6a3d24b43f7c0b780226ad75f63b9f2dd

Tx prefix hash: 640e683d68fccd8a0f61c6499414a2f8ce2ef775c838b0d867ca19d80f088538
Tx public key: 366c817e9fbed8c423c72b7e0c9f4cb0a662dfb73488dc95e92540aeb1da36eb
Timestamp: 1722816887 Timestamp [UCT]: 2024-08-05 00:14:47 Age [y:d:h:m:s]: 00:247:04:52:04
Block: 1080903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176572 RingCT/type: yes/0
Extra: 01366c817e9fbed8c423c72b7e0c9f4cb0a662dfb73488dc95e92540aeb1da36eb021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d299c1985cba0a12cf3f1f059c7c2ac41d43077d073ea782ba53d374cc282240 0.600000000000 1554442 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": 1080913, "vin": [ { "gen": { "height": 1080903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d299c1985cba0a12cf3f1f059c7c2ac41d43077d073ea782ba53d374cc282240" } } ], "extra": [ 1, 54, 108, 129, 126, 159, 190, 216, 196, 35, 199, 43, 126, 12, 159, 76, 176, 166, 98, 223, 183, 52, 136, 220, 149, 233, 37, 64, 174, 177, 218, 54, 235, 2, 17, 0, 0, 0, 9, 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