Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81961769a977f2d90313f7929bd805814b53d582c4eacc8149d582a0453afd07

Tx prefix hash: 5fa99696c6309abf628da9fd646b1e541aef231dbd4dd0e51e7a117d10c29c45
Tx public key: d1a3c9fd7c7ace22e826ade3895b744dd24b0120fb03480d28c2830184303f62
Timestamp: 1732774380 Timestamp [UCT]: 2024-11-28 06:13:00 Age [y:d:h:m:s]: 00:133:16:35:58
Block: 1163362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95356 RingCT/type: yes/0
Extra: 01d1a3c9fd7c7ace22e826ade3895b744dd24b0120fb03480d28c2830184303f620211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 768edfda2608d3bf1d97960378d1ba4147200d7e9f69cb9fa5124d9b436fce43 0.600000000000 1649029 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": 1163372, "vin": [ { "gen": { "height": 1163362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "768edfda2608d3bf1d97960378d1ba4147200d7e9f69cb9fa5124d9b436fce43" } } ], "extra": [ 1, 209, 163, 201, 253, 124, 122, 206, 34, 232, 38, 173, 227, 137, 91, 116, 77, 210, 75, 1, 32, 251, 3, 72, 13, 40, 194, 131, 1, 132, 48, 63, 98, 2, 17, 0, 0, 0, 6, 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