Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e998d75b785108d768ad18f68f24ae56cc604b5e490050d21765667c0b6082f5

Tx prefix hash: a66ac9e199e0c3f4d19677eeb42ea4cbe0476fc8aa88e667dc4049696e3fb69d
Tx public key: 93826e424fabb4a6c59b2982e921c07bc6d72f7110224c82cba9cc90a188d3e5
Timestamp: 1708558904 Timestamp [UCT]: 2024-02-21 23:41:44 Age [y:d:h:m:s]: 01:084:20:47:37
Block: 962703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321702 RingCT/type: yes/0
Extra: 0193826e424fabb4a6c59b2982e921c07bc6d72f7110224c82cba9cc90a188d3e50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c19823f29dfaab8d284acf62c926b0c1751eec358c44e7f4d519ba3e7ac915b8 0.600000000000 1422386 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": 962713, "vin": [ { "gen": { "height": 962703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c19823f29dfaab8d284acf62c926b0c1751eec358c44e7f4d519ba3e7ac915b8" } } ], "extra": [ 1, 147, 130, 110, 66, 79, 171, 180, 166, 197, 155, 41, 130, 233, 33, 192, 123, 198, 215, 47, 113, 16, 34, 76, 130, 203, 169, 204, 144, 161, 136, 211, 229, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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