Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4ec66c1443777f546d39dcab071241733b70d440c5a54c569a64f8d93a13a7

Tx prefix hash: e7b0186bd73c7d50864c0db520111d540ed455106f52470009dd1f52357f9ade
Tx public key: 5a65e5a7dd3980e94c548f6f6432dea2ff0815da36f152e8f0faa74e35a0cbab
Timestamp: 1645837622 Timestamp [UCT]: 2022-02-26 01:07:02 Age [y:d:h:m:s]: 03:017:14:05:51
Block: 446559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 792642 RingCT/type: yes/0
Extra: 015a65e5a7dd3980e94c548f6f6432dea2ff0815da36f152e8f0faa74e35a0cbab021100000002a272b9cb000000000000000000

1 output(s) for total of 20.340655356000 dcy

stealth address amount amount idx
00: 5391a30274867ce5e8084d9fcb692f17afa6fb99d2acafe4a0556619fdceea2b 20.340655356000 860478 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": 446569, "vin": [ { "gen": { "height": 446559 } } ], "vout": [ { "amount": 20340655356, "target": { "key": "5391a30274867ce5e8084d9fcb692f17afa6fb99d2acafe4a0556619fdceea2b" } } ], "extra": [ 1, 90, 101, 229, 167, 221, 57, 128, 233, 76, 84, 143, 111, 100, 50, 222, 162, 255, 8, 21, 218, 54, 241, 82, 232, 240, 250, 167, 78, 53, 160, 203, 171, 2, 17, 0, 0, 0, 2, 162, 114, 185, 203, 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