Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb708fa11634575737a8995935a9b960d0cbbc284d44b2d896cd4856b35b57c2

Tx prefix hash: 588e825ab766c5c52ade4f22bc85bda823b8e9cd3b405d7b90cb7081aaf10bc0
Tx public key: 9020e91eded08a8028617906e1baf62a77094eceb85d2def0fa9c9fa5f3e5714
Timestamp: 1722580289 Timestamp [UCT]: 2024-08-02 06:31:29 Age [y:d:h:m:s]: 00:246:10:11:56
Block: 1078943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176023 RingCT/type: yes/0
Extra: 019020e91eded08a8028617906e1baf62a77094eceb85d2def0fa9c9fa5f3e5714021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e9e1a6532d50e07b2ba97eaecb5415314e786a14484d683b9db38ab5a482e59 0.600000000000 1551686 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": 1078953, "vin": [ { "gen": { "height": 1078943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e9e1a6532d50e07b2ba97eaecb5415314e786a14484d683b9db38ab5a482e59" } } ], "extra": [ 1, 144, 32, 233, 30, 222, 208, 138, 128, 40, 97, 121, 6, 225, 186, 246, 42, 119, 9, 78, 206, 184, 93, 45, 239, 15, 169, 201, 250, 95, 62, 87, 20, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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