Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1f751fbda0a3c0682312d139a42bbebf88730ed72b1c3a8236b62f332f1e3f

Tx prefix hash: 11ad2febaa1d2b5855fbcef2422c666650858f2dc1321c671296cef3a2dc17f6
Tx public key: 31936120b4c5efc63f9ccf32f1d2423829199ad6b67becbd8e42324bd1662d27
Timestamp: 1730655622 Timestamp [UCT]: 2024-11-03 17:40:22 Age [y:d:h:m:s]: 00:065:06:25:10
Block: 1145812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46694 RingCT/type: yes/0
Extra: 0131936120b4c5efc63f9ccf32f1d2423829199ad6b67becbd8e42324bd1662d270211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2898a42b5dac7b4b3dabe9e1c92b877112a9eac4f27867830619d86186e868d9 0.600000000000 1630329 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": 1145822, "vin": [ { "gen": { "height": 1145812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2898a42b5dac7b4b3dabe9e1c92b877112a9eac4f27867830619d86186e868d9" } } ], "extra": [ 1, 49, 147, 97, 32, 180, 197, 239, 198, 63, 156, 207, 50, 241, 210, 66, 56, 41, 25, 154, 214, 182, 123, 236, 189, 142, 66, 50, 75, 209, 102, 45, 39, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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