Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eca2b7116a76d456511f7a34e0e6ebf1b90a6b5c8d3f959a109f50cf2e632b4

Tx prefix hash: 9ab5cd2b6a5193b33afdaf0a5333c55e2f35bd809be07255d8f51b6c2a3d6f9c
Tx public key: fd06790323e8f520e1e8a9d6d64ea0dc8846810c1f8077e037c3b342025b76eb
Timestamp: 1714291267 Timestamp [UCT]: 2024-04-28 08:01:07 Age [y:d:h:m:s]: 00:259:01:53:31
Block: 1010224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185440 RingCT/type: yes/0
Extra: 01fd06790323e8f520e1e8a9d6d64ea0dc8846810c1f8077e037c3b342025b76eb02110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 011e5ad172e0914cef154829cdf7783694220c1ea9783cf2c13436a24db30473 0.600000000000 1472118 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": 1010234, "vin": [ { "gen": { "height": 1010224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "011e5ad172e0914cef154829cdf7783694220c1ea9783cf2c13436a24db30473" } } ], "extra": [ 1, 253, 6, 121, 3, 35, 232, 245, 32, 225, 232, 169, 214, 214, 78, 160, 220, 136, 70, 129, 12, 31, 128, 119, 224, 55, 195, 179, 66, 2, 91, 118, 235, 2, 17, 0, 0, 0, 16, 89, 218, 211, 245, 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