Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7f8caea5bd6476d50e47585768fd167bc58f8c81a27e597190bb18259c120f7

Tx prefix hash: daab6fe25d05e2cec410dd87336d728cf13e19e36ff8ffd996eee92292887bf9
Tx public key: e0dbc75da87b56f8c6d7fa38d369ad6c2bc4e3757615c01f3385ae12e1b4aafd
Timestamp: 1735829610 Timestamp [UCT]: 2025-01-02 14:53:30 Age [y:d:h:m:s]: 00:115:09:02:20
Block: 1188659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82268 RingCT/type: yes/0
Extra: 01e0dbc75da87b56f8c6d7fa38d369ad6c2bc4e3757615c01f3385ae12e1b4aafd021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 366a85251649046acaca641ba009be59c233fd32eea3af0f056344858f251aee 0.600000000000 1675162 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": 1188669, "vin": [ { "gen": { "height": 1188659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "366a85251649046acaca641ba009be59c233fd32eea3af0f056344858f251aee" } } ], "extra": [ 1, 224, 219, 199, 93, 168, 123, 86, 248, 198, 215, 250, 56, 211, 105, 173, 108, 43, 196, 227, 117, 118, 21, 192, 31, 51, 133, 174, 18, 225, 180, 170, 253, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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