Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a1d965a63a9037ac2f9505e0b4f792510b8e311083651ee190dee6bfc001f4c

Tx prefix hash: 1bdc4d7b740fcda8fb9b7b3d071bcb4c142edb70e784ffda1c2bc08fc340e6ad
Tx public key: d0aa0af112dbc666915cfc355343ea5c15c7cfef752e8c9ea2f27002ea41714a
Timestamp: 1658174210 Timestamp [UCT]: 2022-07-18 19:56:50 Age [y:d:h:m:s]: 03:105:20:34:55
Block: 546641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 855410 RingCT/type: yes/0
Extra: 01d0aa0af112dbc666915cfc355343ea5c15c7cfef752e8c9ea2f27002ea41714a021100000007bf7ee4e7000000000000000000

1 output(s) for total of 9.478761212000 dcy

stealth address amount amount idx
00: 3eef7e1275cbf3c6c7f4138ce677c0aaf489081afd16a0f0907f6f13028c1567 9.478761212000 977680 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": 546651, "vin": [ { "gen": { "height": 546641 } } ], "vout": [ { "amount": 9478761212, "target": { "key": "3eef7e1275cbf3c6c7f4138ce677c0aaf489081afd16a0f0907f6f13028c1567" } } ], "extra": [ 1, 208, 170, 10, 241, 18, 219, 198, 102, 145, 92, 252, 53, 83, 67, 234, 92, 21, 199, 207, 239, 117, 46, 140, 158, 162, 242, 112, 2, 234, 65, 113, 74, 2, 17, 0, 0, 0, 7, 191, 126, 228, 231, 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