Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ac541d2ae2827638126fce02e9ea3d72ddd1025e1fb07861bfd898550b597eb

Tx prefix hash: 0024308515e6743011044f2e2d7f58efc8df771598d0a2b42683bba07e9d891b
Tx public key: 4f3158750b90fcb600dbbf05a2de816fcfa8266b0233e7105cec0e9e596cdcc8
Timestamp: 1720647532 Timestamp [UCT]: 2024-07-10 21:38:52 Age [y:d:h:m:s]: 00:263:20:49:30
Block: 1062928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188513 RingCT/type: yes/0
Extra: 014f3158750b90fcb600dbbf05a2de816fcfa8266b0233e7105cec0e9e596cdcc8021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d5e7bd0c9cde77f32dd5290ad266e26ae43e6759a752f895b5ad4e6e43f12de 0.600000000000 1533439 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": 1062938, "vin": [ { "gen": { "height": 1062928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d5e7bd0c9cde77f32dd5290ad266e26ae43e6759a752f895b5ad4e6e43f12de" } } ], "extra": [ 1, 79, 49, 88, 117, 11, 144, 252, 182, 0, 219, 191, 5, 162, 222, 129, 111, 207, 168, 38, 107, 2, 51, 231, 16, 92, 236, 14, 158, 89, 108, 220, 200, 2, 17, 0, 0, 0, 1, 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