Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b206e827dfcbd1846fde39e688064cffc5416a1be0ac3141a16086247d36879

Tx prefix hash: e5ed588460b57aee0f1f955d5a5138f4e3dc5ed1b9a970839be73a83d5e7c43f
Tx public key: 931b7e59e6c308134d52b2d8eb12702b181402301616a07974b7f8ab4b70a6ec
Timestamp: 1728913991 Timestamp [UCT]: 2024-10-14 13:53:11 Age [y:d:h:m:s]: 00:101:17:30:43
Block: 1131460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72672 RingCT/type: yes/0
Extra: 01931b7e59e6c308134d52b2d8eb12702b181402301616a07974b7f8ab4b70a6ec021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f60b0645b2bec80c1f03c42673389833082bc23b8de359e55dc2ac52f450207 0.600000000000 1614363 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": 1131470, "vin": [ { "gen": { "height": 1131460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f60b0645b2bec80c1f03c42673389833082bc23b8de359e55dc2ac52f450207" } } ], "extra": [ 1, 147, 27, 126, 89, 230, 195, 8, 19, 77, 82, 178, 216, 235, 18, 112, 43, 24, 20, 2, 48, 22, 22, 160, 121, 116, 183, 248, 171, 75, 112, 166, 236, 2, 17, 0, 0, 0, 4, 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