Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eed1ce0df8a8d5b2c6fe3fd9d6224e06832d31788db440ed88dd7a4332e512ad

Tx prefix hash: 878f6f2ee3c6f3d21e259268fc44c895cf53ba5153b7550755a8cdfb76127a0a
Tx public key: 4164b635ac901c38eafcc60e6f2928455a7f0087ce8a6c400eca725325cf3fcc
Timestamp: 1717253074 Timestamp [UCT]: 2024-06-01 14:44:34 Age [y:d:h:m:s]: 00:296:18:07:55
Block: 1034788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212071 RingCT/type: yes/0
Extra: 014164b635ac901c38eafcc60e6f2928455a7f0087ce8a6c400eca725325cf3fcc02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5cd0f1bd5c37dfcb356123f381037c0e102473e41cda7d5bf8f3e6f18b5f73c 0.600000000000 1503307 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": 1034798, "vin": [ { "gen": { "height": 1034788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5cd0f1bd5c37dfcb356123f381037c0e102473e41cda7d5bf8f3e6f18b5f73c" } } ], "extra": [ 1, 65, 100, 182, 53, 172, 144, 28, 56, 234, 252, 198, 14, 111, 41, 40, 69, 90, 127, 0, 135, 206, 138, 108, 64, 14, 202, 114, 83, 37, 207, 63, 204, 2, 17, 0, 0, 0, 5, 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