Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9feeb7112e16e4777b06d301ce3a39bcd4302b64354b8843731cdee33e0e646

Tx prefix hash: 60a50a2c4db31944cd400199e182467adee7442a70b92f0751d221bddb2c16c7
Tx public key: 4031c58f8cda7e41d2774faa6c2a02e6a295fa28281cd83a48ece511f4af149a
Timestamp: 1686114351 Timestamp [UCT]: 2023-06-07 05:05:51 Age [y:d:h:m:s]: 01:352:13:59:32
Block: 776870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513216 RingCT/type: yes/0
Extra: 014031c58f8cda7e41d2774faa6c2a02e6a295fa28281cd83a48ece511f4af149a021100000002faf35c9c000000000000000000

1 output(s) for total of 1.636467406000 dcy

stealth address amount amount idx
00: a7912a28fcdd745f6a94d19db4a2afa39a420c46ca215ca9bbafcb55a7a5d8d4 1.636467406000 1226437 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": 776880, "vin": [ { "gen": { "height": 776870 } } ], "vout": [ { "amount": 1636467406, "target": { "key": "a7912a28fcdd745f6a94d19db4a2afa39a420c46ca215ca9bbafcb55a7a5d8d4" } } ], "extra": [ 1, 64, 49, 197, 143, 140, 218, 126, 65, 210, 119, 79, 170, 108, 42, 2, 230, 162, 149, 250, 40, 40, 28, 216, 58, 72, 236, 229, 17, 244, 175, 20, 154, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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