Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd3301aa8f8de40cd256d371605ba3e29666e0072e4780a54a70d93d81ce7ad

Tx prefix hash: 8498612462e3a00693122c52097b1baa506a01bb9ac528002a846f38f014c7a3
Tx public key: a3fa667bce0808c7c0aa0536594e0d6638d308c4702bf45838dc2579ef30b249
Timestamp: 1720579806 Timestamp [UCT]: 2024-07-10 02:50:06 Age [y:d:h:m:s]: 00:262:17:58:40
Block: 1062369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187717 RingCT/type: yes/0
Extra: 01a3fa667bce0808c7c0aa0536594e0d6638d308c4702bf45838dc2579ef30b249021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23bf8396ea2ed2d17d9a64149f579b7899cde47f1b9e7aaeaeea2b0f21a86c4c 0.600000000000 1532870 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": 1062379, "vin": [ { "gen": { "height": 1062369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23bf8396ea2ed2d17d9a64149f579b7899cde47f1b9e7aaeaeea2b0f21a86c4c" } } ], "extra": [ 1, 163, 250, 102, 123, 206, 8, 8, 199, 192, 170, 5, 54, 89, 78, 13, 102, 56, 211, 8, 196, 112, 43, 244, 88, 56, 220, 37, 121, 239, 48, 178, 73, 2, 17, 0, 0, 0, 2, 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