Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8c9deed3f287d1605556fe1f77c69accf4f27e7cb0db9074655d7dce9ab7738

Tx prefix hash: 970489f5f5721c45b5b6c8803b855ba4e27f934551c7693af686144cd0a039a1
Tx public key: 5e2255b8e60191f8b3879ebc2c3569e99060ccd69182456c25f2fc22076dce67
Timestamp: 1694018737 Timestamp [UCT]: 2023-09-06 16:45:37 Age [y:d:h:m:s]: 01:133:20:50:31
Block: 842339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357007 RingCT/type: yes/0
Extra: 015e2255b8e60191f8b3879ebc2c3569e99060ccd69182456c25f2fc22076dce6702110000000b33af99f4000000000000000000

1 output(s) for total of 0.993073263000 dcy

stealth address amount amount idx
00: 93c65f9d73b027179fb7fa377011d0d537f4027facff7f38a83774e59aeeb91d 0.993073263000 1295455 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": 842349, "vin": [ { "gen": { "height": 842339 } } ], "vout": [ { "amount": 993073263, "target": { "key": "93c65f9d73b027179fb7fa377011d0d537f4027facff7f38a83774e59aeeb91d" } } ], "extra": [ 1, 94, 34, 85, 184, 230, 1, 145, 248, 179, 135, 158, 188, 44, 53, 105, 233, 144, 96, 204, 214, 145, 130, 69, 108, 37, 242, 252, 34, 7, 109, 206, 103, 2, 17, 0, 0, 0, 11, 51, 175, 153, 244, 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