Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4eac3a05afbfa268ef6e4d3cb48a1746f3f9a5758edd448bfe2281a438148850

Tx prefix hash: 2c78544e339b38f23df3c83b74b8b127cfe1eee1d81563d479392d1e1e6d01dd
Tx public key: 1b22f2cdf415a60066029a73e8182667985e4b41d0300859f8a4a4fa1c1a6f44
Timestamp: 1626677317 Timestamp [UCT]: 2021-07-19 06:48:37 Age [y:d:h:m:s]: 03:230:12:56:35
Block: 296761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 936125 RingCT/type: yes/0
Extra: 011b22f2cdf415a60066029a73e8182667985e4b41d0300859f8a4a4fa1c1a6f4402110000003306faf294000000000000000000

1 output(s) for total of 63.789305373000 dcy

stealth address amount amount idx
00: dc0a43406676f3a5a2f0f90318f287c2adf6f1baf2049f839620432b8ed2fae0 63.789305373000 621201 of 0

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": 296771, "vin": [ { "gen": { "height": 296761 } } ], "vout": [ { "amount": 63789305373, "target": { "key": "dc0a43406676f3a5a2f0f90318f287c2adf6f1baf2049f839620432b8ed2fae0" } } ], "extra": [ 1, 27, 34, 242, 205, 244, 21, 166, 0, 102, 2, 154, 115, 232, 24, 38, 103, 152, 94, 75, 65, 208, 48, 8, 89, 248, 164, 164, 250, 28, 26, 111, 68, 2, 17, 0, 0, 0, 51, 6, 250, 242, 148, 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