Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e4c4535ed576312980891d86caea3a734c53273f52e7d0ce8e75cff4fdea53

Tx prefix hash: e00c02c33d1b84b7c5a772d80f2927a2fe19e787f3f69a893a5e24d9cda51128
Tx public key: e4a3f8b71d2dc361f4b6e5127771e90bc0e86b45d5645d743fb593a8513fec29
Timestamp: 1630768987 Timestamp [UCT]: 2021-09-04 15:23:07 Age [y:d:h:m:s]: 03:251:12:31:53
Block: 327389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 954373 RingCT/type: yes/0
Extra: 01e4a3f8b71d2dc361f4b6e5127771e90bc0e86b45d5645d743fb593a8513fec2902110000008ddeae9d30000000000000000000

1 output(s) for total of 50.493137426000 dcy

stealth address amount amount idx
00: 920945f725d1632897b3b40b3e6392008965d6bd8b69455d10c880051f79252e 50.493137426000 678022 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": 327399, "vin": [ { "gen": { "height": 327389 } } ], "vout": [ { "amount": 50493137426, "target": { "key": "920945f725d1632897b3b40b3e6392008965d6bd8b69455d10c880051f79252e" } } ], "extra": [ 1, 228, 163, 248, 183, 29, 45, 195, 97, 244, 182, 229, 18, 119, 113, 233, 11, 192, 232, 107, 69, 213, 100, 93, 116, 63, 181, 147, 168, 81, 63, 236, 41, 2, 17, 0, 0, 0, 141, 222, 174, 157, 48, 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