Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f6abe70e2bc4059d1f5abea787973378c7129dbba4735aa722118cfc88447ae

Tx prefix hash: ea510e5113bf9b143f86976959e63c7177b9f76d286ca6bcc68f70679ec0ac81
Tx public key: dbd8d9d97a6e5b3d89c77e4c3491583ed5a3d15e7e8196e35f20d9bf2686ce26
Timestamp: 1581918570 Timestamp [UCT]: 2020-02-17 05:49:30 Age [y:d:h:m:s]: 04:326:09:19:44
Block: 66525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125726 RingCT/type: yes/0
Extra: 01dbd8d9d97a6e5b3d89c77e4c3491583ed5a3d15e7e8196e35f20d9bf2686ce26021100000004d81c26c0000000000000000000

1 output(s) for total of 369.467181816000 dcy

stealth address amount amount idx
00: 7c958e61254609f5e04d00ec489689b4fa50d2dad17145d12bc5f4ca61b1b482 369.467181816000 122550 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": 66535, "vin": [ { "gen": { "height": 66525 } } ], "vout": [ { "amount": 369467181816, "target": { "key": "7c958e61254609f5e04d00ec489689b4fa50d2dad17145d12bc5f4ca61b1b482" } } ], "extra": [ 1, 219, 216, 217, 217, 122, 110, 91, 61, 137, 199, 126, 76, 52, 145, 88, 62, 213, 163, 209, 94, 126, 129, 150, 227, 95, 32, 217, 191, 38, 134, 206, 38, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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