Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17c3698fc829b18cb701922e33845d833820c2a20273b245899f8241a7c058a6

Tx prefix hash: 6c1a157ea69b1b77225c5ad8c5e2a5923789e2bd72b2574d7f3fde50c27ed8ba
Tx public key: bf47859b87f971e4c099b66fd1f0d2a303f035bdddc6e606569f573f9fed8831
Timestamp: 1714130819 Timestamp [UCT]: 2024-04-26 11:26:59 Age [y:d:h:m:s]: 00:202:23:03:54
Block: 1008897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145289 RingCT/type: yes/0
Extra: 01bf47859b87f971e4c099b66fd1f0d2a303f035bdddc6e606569f573f9fed88310211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 019381e185697ee8775db16e75e822671b7760c0e50a3cca41171dd52410a0f7 0.600000000000 1470401 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": 1008907, "vin": [ { "gen": { "height": 1008897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "019381e185697ee8775db16e75e822671b7760c0e50a3cca41171dd52410a0f7" } } ], "extra": [ 1, 191, 71, 133, 155, 135, 249, 113, 228, 192, 153, 182, 111, 209, 240, 210, 163, 3, 240, 53, 189, 221, 198, 230, 6, 86, 159, 87, 63, 159, 237, 136, 49, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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