Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b42b5e11635bde8074c0008f4d8314104494407f2255eb88d4fa5293de709c6

Tx prefix hash: f8abc1a71ef1279c1cbcc20f3834a4976ea81c74681aa3787935be251eb092a8
Tx public key: d5a13927a12527d9dae89b31a963fbdf42841beddc9d3df86444d594098f1f38
Timestamp: 1727579723 Timestamp [UCT]: 2024-09-29 03:15:23 Age [y:d:h:m:s]: 00:192:19:19:10
Block: 1120397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137600 RingCT/type: yes/0
Extra: 01d5a13927a12527d9dae89b31a963fbdf42841beddc9d3df86444d594098f1f38021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac749f6d15471ce5a8b5d619278f053803ca8fdb7b7fd08d7ed9cd1fd0c594d0 0.600000000000 1602300 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": 1120407, "vin": [ { "gen": { "height": 1120397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac749f6d15471ce5a8b5d619278f053803ca8fdb7b7fd08d7ed9cd1fd0c594d0" } } ], "extra": [ 1, 213, 161, 57, 39, 161, 37, 39, 217, 218, 232, 155, 49, 169, 99, 251, 223, 66, 132, 27, 237, 220, 157, 61, 248, 100, 68, 213, 148, 9, 143, 31, 56, 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